-
-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use gcp sdk provided flow for obtaininng application default credenti… #430
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems like a great improvement.
- Do we need to bump the minimum version of the
google.auth
dependency to support this? - Can you fix up the tests, specifically the skip when missing credentials?
- Can you verify that tests pass locally for you?
@jacobtomlinson, fixing the test requires supporting an older version of |
However, I see that the minimum required version supports the used method |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've fixed things up in the CI here, but there are now conflicts. @dbalabka would you mind polishing this up and getting it ready for another review?
@jacobtomlinson , thanks for the reminder. I belive I can get back to the PR improvements next week. In our case, I've started to use a service account; however, it is not the best option for local development according to GCP recommendation because the service account isn't tight with the developer's account: https://cloud.google.com/docs/authentication/provide-credentials-adc#local-dev:~:text=when%20your%20code%20is%20running%20in%20a%20local%20development%20environment%2C%20such%20as%20a%20development%20workstation%2C%20the%20best%20option%20is%20to%20use%20the%20credentials%20associated%20with%20your%20user%20account. |
@jacobtomlinson , seems GCP tests are all skipped in test env. I've tried to run cluster locally and get a weird error. Can it be the old image reason?
|
Yeah quite possibly! But if you got that far in the test then the Dask cluster deployed successfully. We should dig into what is happening here (I assume you have a different Python version locally than the one in the container), but I don't want that to hold up this PR. |
…als (#429)